Replace Content in PRE Tags with HTML Entities
If you have a website that relies heavily on PRE tags, you know the important of converting PRE tag content to their HTML entities. Doing so prevents worlds of possible rendering issues. The following PHP snippet HTML-Entitizes (?) any code within PRE tags:
//replaces pre content with html entities
function pre_entities($matches) {
return str_replace($matches[1],htmlentities($matches[1]),$matches[0]);
}
//to html entities; assume content is in the "content" variable
$content = preg_replace_callback('/<pre.*?>(.*?)<\/pre>/imsu',pre_entities, $content);
I use this for just about every post I write. You could also stick this in your CMS if you have clients that may have use for PRE tags.
![5 Ways that CSS and JavaScript Interact That You May Not Know About]()
CSS and JavaScript: the lines seemingly get blurred by each browser release. They have always done a very different job but in the end they are both front-end technologies so they need do need to work closely. We have our .js files and our .css, but...
![Interview with a Pornhub Web Developer]()
Regardless of your stance on pornography, it would be impossible to deny the massive impact the adult website industry has had on pushing the web forward. From pushing the browser's video limits to pushing ads through WebSocket so ad blockers don't detect them, you have...
![iPhone Click Effect Using MooTools or jQuery]()
One thing I love about love about Safari on the iPhone is that Safari provides a darkened background effect when you click a link. It's the most subtle of details but just enforces than an action is taking place. So why not implement that...
![CSS content and attr]()
CSS is becoming more and more powerful but in the sense that it allows us to do the little things easily. There have been larger features added like transitions, animations, and transforms, but one feature that goes under the radar is generated content. You saw a...
Beware that having someting like “something” in another would leave you with one opening and two closings. If this is a possible usecase, you might use a regex like this :
/(.*?[.*]*)/imsu
…but it still wouldn’t handle the case of having a single closing tag inside another . Could someone manage to write a regex which would handle this case ?
The function name (pre_entities) should be between quotes otherwise it will throw a notice.
Beware that having a pre tag inside another pre tag would leave you with one pre opening and two pre closings. If this is a possible usecase, you might use a regex like this :
/<pre.*?>(.*?[<pre.*?>.*<\/pre>]*)<\/pre>/imsu
The tags got stripped in my first comment, sorry about that, if htmlentities show up in the regex, replace them with the good characters …but it still wouldn’t handle the case of having a single closing pre tag inside another pre. Could someone manage to write a regex which would handle this case ?
The function name (pre_entities) should be between quotes otherwise it will throw a notice.
It works as long as you don’t have nested <pre> tags.
I wrote about this on my blog but the only real way to do it is to use an XML parser.
One issue to watch out for is to not encode any of the content before this is run, as it will double-entitize the ampersand e.g., &.
Also, would there be any issues if not matches are found?
To solve the nested ‘pre’ tag issue, just use some non-standard tags that you’re sure won’t be in your content, rather than ‘pre’ (i.e. ‘mycode’). Your regular expression then becomes a match for the ‘mycode’ tags, and you can immediately follow it up with another preg_replace () to turn the ‘mycode’ tags into ‘pre’ tags after you’re done htmlentitizing the content.
I’ve been using elliotswan.com/postable. It seems to get the job done for me. But it’s nice to know this option.
Could someone explain how to fix the following notice?
Notice: Use of undefined constant pre_entities – assumed ‘pre_entities’ in C:\wamp\www\example.com\admin\get_posts.php on line 16
doh! put quotes on ‘pre_entities’, fixes it. Thanks David! Great snippet.
Thank you for the tip! I couldn’t find what was going wrong with the HTML…